All Things Open 2018: How to open source an internal project
Publication date 2018-10-22
Topics software development, open source, free software, free and open source software, FOSS, F/LOSS, OSS, ATO, All Things Open, ATO2018
So your company is going to release an internal project as open source. Are you ready for your new responsibilities? You could just throw the code up on a forge like GitHub or GitLab, but it’s unlikely to receive attention or provide much benefit to the company.
Open sourcing an internal project requires a lot of thought and work. Releasing a project as open source requires changes to the development, build, and release workflow. This is not about the code per se; it’s the processes and infrastructure that surround the code that make the project successful.
VM Brasseur discusses what you need to know and what to expect before you release your internal project.
- Identifying company goals for the project
- Prerelease due diligence (licenses and code hygiene)
- Community expectations and maintenance
- Processes that need to happen in the open
- Communication (internal and external)
Ocr ABBYY FineReader 11.0 (Extended OCR)
Scanner VM Brasseur
ABBYY GZ Uplevel BACK
FULL TEXT Uplevel BACK
H.264 Uplevel BACK
OGG VIDEO Uplevel BACK
PDF Uplevel BACK
QUICKTIME Uplevel BACK
SINGLE PAGE PROCESSED JP2 ZIP Uplevel BACK
Uploaded by VMBrasseur on